update docs to use latest version, not a future version#14
Merged
alexrashed merged 1 commit intolocalstack:mainfrom Apr 10, 2024
Merged
Conversation
alexrashed
approved these changes
Apr 10, 2024
Member
alexrashed
left a comment
alexrashed
left a comment
There was a problem hiding this comment.
The next version slipped into the readme with #9, but wasn't released yet.
Thanks a lot for your contribution, proactively fixing the README such that other people won't run into the same issue! 🦸🏽
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It looks like the README specifies version 0.1.3 for the action. Per the marketplace website, the latest version is 0.1.2. This PR updates the readme to use the latest version instead of a future one.